QRZ! Ham Radio 5/QRZ Ham Radio Callsign Database - Volume 5.iso/digests/tcp/940011.txt

Internet Message Format | 1994-11-13 | 18.4 KB

Date: Sat, 15 Jan 94 04:30:02 PST
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #11
To: tcp-group-digest


TCP-Group Digest            Sat, 15 Jan 94       Volume 94 : Issue   11

Today's Topics:
                  Connecting the client to the radio
                        Here we go... (gone?)
                 Internet/AMPRnet gateway question...
                          JNOS and BPQ Code
                               NOS help
                           Packet Drivers
                       TCP-Group Digest V94 #10
                       TCP-Group Digest V94 #8
                   TCP/IP AMPRnet publicity effort
                                TNC3?

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Fri, 14 Jan 94 14:01:46 -0500
From: [e-mail] (Gary Grebus)
Subject: Connecting the client to the radio
To: [e-mail]

Has anyone looked into what it would take to "radio-ify" (how's that
for a word) one of the existing free TCP/IP implementations for
DOS/Windows?  From what I've seen, there are nice, friendly clients
available that layer on top of packages like WATTCP,
which then use the packet driver interface to talk to hardware.

Is anyone familiar enough with these packages to speculate on whether
it would be feasible to make one radio-capable?  The things I can
think of that would require attention are:

1.  Adding rudimentary AX.25 link layer support.

2.  Finding a packet driver for an existing adapter or KISS serial port.

3.  Cleaning up any fast-link/low-error-rate biases in the TCP implementation.

I'm assuming server functions are provided by a different platform,
and that link speeds are reasonable (9.6 kb/s or greater).

It seems like much of ham TCP/IP development has single-streamed
because the KA9Q code is the only radio-capable software.

Yours in curiosity,

    /gary
    K8LT

Gary L. Grebus                Voice: [phone]
Digital Equipment Corporation        FAX:   [phone]
[e-mail]

------------------------------

Date: Fri, 14 Jan 94 12:56:38 EST
From: [e-mail] (D. Crompton)
Subject: Here we go... (gone?)
To: [e-mail]

Working for the government it seems that whenever people do not have
anything (or little) to do they become dangerous. 10 years ago they
should have worried about security! Now the cold war is over and there
is an excess of DOD personel, and you know what that means...


DOD plan may cut ties to Internet

BY ELLEN MESSMER
Washington, D.C.

The Defense Information Systems Agency (DISA), which handles net planning
for the Department of Defense, is coming under fire for a plan to tighten
security by cutting users in the military offfrom direct Internet access.

Revealed in a brief internal announcement late last year, DISA's plan has
provoked an uproar from users on the worldwide Defense Data Network (DDN),
which today connects directly to the Internet. The proposal is intended to
prevent security breaches and keep computer viruses from getting into defense
systems. It would require a change of Internet addresses for military users.

Critics are calling the plan technically inept and overly restrictive and
saying it could make it harder for companies to do business electronically
with the Defense  Department. DISA intends to set up a DDN gateway that
will require anyone sending I lectronic mail messages to the military to
alter the recipient's network address. "Exchange of electronic mail between
he Department of Defense and Internet will be allowed, but to communicate
through the gateway, E-mail users would have to know which network the E-mail
receiver is on in order to direct mail through the mail relay, " said the
statement issued by DISA representative Robert NcNab.

Network managers within the military and outside assert that such a gateway
would cause severe E-mail congestion and may be technically infeasible.
Experts point out that private-sector companies usually solve the Internet
security problem through commercially available "fire walls," mail exchange
(MX) record servers that do not require changes to internet addresses.
"Putting in a firewall is a good thing to do, "said  Stephen Williams,
president of the Local Internet Gateway Co. in Dayton, Ohio, who said
about a half dozen vendors sell MX server fire walls. Williams pointed
out that Mead Data Central, Inc. has just installed Eagle Software, Inc.'s
fire wall, while General Electric Corp. has long used one.

One military source points out that DISA's plan--which would still allow
users to use File Transfer Protocol and Telnet to external databases is
more relaxed than separating the DDN from the Internet. Many military users,
fearing retribution from Defense Department authorities, say privately they
would deeply regret losing their Internet freedom.

But security is a double-edged sword, pointed out Internet Society President
Vinton Cerf who last week joined MCI Communications Corp. as senior vice
president of data architecture. "When you're dealing with security questions,
the more isolatedyou are, the more comfortable the security people get,
" Cerf said. "But being part of a larger system can give you access to
communications facilities you might needin a hostile environment. So it's
not a simple choice for the military to make."

Leaked Defense Department E-mail suggests DISA made its decision about
disconnecting the DDN without informing the Pentagon, which is now in
the awkward position of explaining DlSA's actions. DISA declined  to
discuss its plan, but documents obtainedby Network World suggest DISA
has already rejected the MX  record server approach.

DISA is also working on a draft E-mail policy that would establish
rules for employee privacy, disclosure requirements and archiving of
E-mail. The draft makes it clear that Defense Department E-mail is for
offical use only and is subject to monitoring.

The future of the DISA gateway relay plan remains unclear. In a statement
that DISA said came from the Office of the Deputy Secretary of Defense,
the Defense Department said DISA is still evaluating "ways to provide
[Defense Department] data networks with safeguards against hacker and
virus penetration" and that "possible implementation dates" are
now underassessment.


>From Network World - January 10th, 1994

------------------------------

Date: Fri, 14 Jan 94 09:54:55 EST
From: [e-mail] (Robert L. Metcalf NV1A)
Subject: Internet/AMPRnet gateway question...
To: [e-mail] (TCP folx)

Hi all!

Is there a FAQ around that says how to configure NOS as a gateway
between Internet and AMPRnet?

Once NOS is configured who does one contact to get this gateway "known"
to other gateways?

Thanks,
Rob NV1A
[e-mail]

------------------------------

Date: Fri, 14 Jan 1994 09:19:05 -0600 (CST)
From: [e-mail] (Steve Sampson)
Subject: JNOS and BPQ Code
To: [e-mail] (Martin Lines)

>
> I originally wrote to the group to find out if anyone has similar problems
> to myself at integrating
> JNOS and BPQ switches. Using the jnos built in bpq support I was unable to
> get an interconnect
> between the two cohabiting switches.
> ...
>
> I have removed all references to the above commands in the autoexec.nos and
> I am happily switching
> between JNOS and BPQ but this is not necessarily ideal.
>
> Anyone have any further ideas/comments?
>

My first suggestion would be to get rid of the BPQ code.  What does the BPQ
code do that causes you to try and glue two pieces together like this?

I'd try and use the Net/Rom code in JNOS or use an X-1 TNC before I'd stick
in a delay-line like BPQ.
--
Steve

------------------------------

Date: Fri, 14 Jan 94 09:02:02 CST
From: Ted Holdahl <[e-mail]>
Subject: NOS help
To: [e-mail]

HELP

------------------------------

Date: Fri, 14 Jan 1994 00:03:24 EST
From: "Russell Nelson" <[e-mail]>
Subject: Packet Drivers
To: [e-mail]

In article <[e-mail] you write:

  > Does anyone know where I can get packet drivers for a
  > 3com 3c523b (microchannel ethernet board) and / or IBM's
  > microchannel token ring board?

Only the 3c523:

-- HOWTOGET.IT

        The Crynwr packet driver collection

Availability

The Crynwr packet driver collection is available on CD-ROM, by mail,
by FTP, by email, by UUCP and by modem.  The drivers are distributed
in three files: pktd11.zip, which contains most executables and
documentation, pktd11a.zip, which contains the first half of the
remaining files, and pktd11b.zip, which contains the second half of
the remaining files.

Mail:

Columbia University distributes packet drivers on PC diskette by
postal mail.  5.25-inch 360K and 3.5" 720K diskettes are available;
please specify size.  Two diskette sets are available, and two prices
are quoted for each; the first price is for the USA, Canada, and
Mexico; the second price is for shipment to all other countries.  All
prices are in US dollars.  Prepayment by check, MasterCard, or Visa
is accepted.  If your check is not drawn on a US bank, please add $35
check-cashing fee.

  1. Binaries and documentation:        $35  /  $40
  2. Source code:                       $60  /  $68

To order by credit card, please specify MasterCard or Visa, your card
number and expiration date, and sign and date your order.  For further
information, call [phone], or write to:

  Kermit Distribution, Dept PD
  Columbia University Academic Information Systems
  612 West 115th Street
  New York, NY  10025

or send e-mail to [e-mail] (Internet) or KERMIT@CUVMA
(BITNET/CREN/EARN).

FTP/email:

The packet driver collection has its own directory devoted to it in
the SimTel collection, msdos/pktdrvr.  The drivers are there, along
with a number of programs that use the packet drivers.

For security reasons the SimTel Software Repository is located on a
host that is not accessible by Internet users, however its files are
available by anonymous ftp from the primary mirror site OAK.Oakland.Edu
(141.210.10.117) located in Rochester, Michigan, and from the secondary
mirror sites:

   St. Louis, MO: wuarchive.wustl.edu (128.252.135.4)
   Corvallis, OR: archive.orst.edu (128.193.2.13)
Falls Church, VA: ftp.uu.net (192.48.96.9
       Australia: archie.au (139.130.4.6)
         England: src.doc.ic.ac.uk (146.169.2.1)
         Finland: ftp.funet.fi (128.214.6.100)
         Germany: ftp.uni-paderborn.de (131.234.2.32)
          Israel: ftp.technion.ac.il (132.68.1.10)
     Switzerland: ftp.switch.ch (130.59.1.40)
          Taiwan: NCTUCCCA.edu.tw (140.111.1.10)

SimTel files may obtained by e-mail from various ftp-mail servers
or through the BITNET/EARN file servers.  For details see file
/pub/msdos/filedocs/mailserv.inf.  Gopher users can access the
collection through Gopher.Oakland.Edu.  World Wide Web (WWW) and
Mosaic users can connect to the URL http://www.acs.oakland.edu to
access the files on OAK.Oakland.Edu.

Modem:

If you cannot access them via FTP or e-mail, most SimTel MSDOS
files, including the PC-Blue collection, are also available for
downloading from Detroit Download Central [phone].  DDC
has multiple lines which support 300/1200/2400/9600/14400 bps
(103/212/V22bis/HST/V32bis/V42bis/MNP).  This is a subscription system
with an average hourly cost of 17 cents.  It is also accessable on
Telenet via PC Pursuit and on Tymnet via StarLink outdial.  New files
uploaded to SimTel are usually available on DDC within 24 hours.

CD-ROM:

Title:  Packet Driver, WinSock & TCP/IP CD-ROM (aka Packet Driver CD)
Price:  US$29.95/each

Brochures and order forms for the CD (paper and electronic versions)
will be available from:

Gopher: gopher.CDPublishing.com
FTP:    ftp.CDPublishing.com
E-mail: <[e-mail]>
FAX:    [phone]
Phone:  [phone]
        800-333-7565
Postal: CD Publishing Corporation
        4824 Fraser Street
        Vancouver, B.C.  V5V 4H4
        Canada

UUCP:

The packet driver files are available from UUNET's 1-900-GOT-SRCS, in
uunet!~/systems/msdos/simtel20/pktdrvr.  Contact UUNET for more details:

UUNET Technologies, Inc.
3110 Fairview Park Drive, Suite 570
Falls Church, VA 22042
[phone] (voice)
[phone] (fax)
[e-mail]

UK UUCP:

Steve Kennedy's BBS is on [phone] (Telebit T2500 PEP/V32 ...)
                                                2455 (USR HST/DS+)

Files will be in /pub
there will be an anonymous uucp (nuucp) account.

System name is "marvin"

-- end of HOWTOGET.IT

--
-russ <[e-mail]>      ftp.msen.com:pub/vendor/crynwr/crynwr.wav
Crynwr Software   | Crynwr Software sells packet driver support.
11 Grant St.      | [phone] (9201 FAX)    | Quakers do it in the light
Potsdam, NY 13676 | LPF member - ask me about the harm software patents do.

------------------------------

Date: Fri, 14 Jan 94 18:54:12 +0100
From: Dirk Slock <[e-mail]>
Subject: TCP-Group Digest V94 #10
To: [e-mail]

unsubscribe [e-mail]

------------------------------

Date: Fri, 14 Jan 94 10:22:25 EST
From: [e-mail] (D. Crompton)
Subject: TCP-Group Digest V94 #8
To: [e-mail], [e-mail]

To N8WEI (and all)

Another topic that has been talked to death! Changing drives at the
ftp server.

The responses you are seeing are perfectly normal in an unmodified
JNOS compile. The 'lcd' command changes the local directory and since
you are the owner any directory/drive is allowed, but for very
understandable security reasons, the 'cd' command is limited to changes
that are established in the SERVERS ftpusers file

yourusername * /pub xxx
anonymous * /pub xxx
specialname pw / 127

These examples of the SERVERS ftpusers file would do the following:

The first example would allow just the person with <yourusername> and
password use the /pub (and lower) directories ONLY

The second would do the same for anonymous logins. The xxx is the permission
read/write/delete and the BBS permission bits.

The third is a dangerous one because it allows that user and password
do go anywhere on the disk and do anything.

Note that none of these allow the user to go anywhere but the NOS
boot drive.

That is what the later modes were about that have been spoken about on
the various groups. Although I have not applied the mods myself someone
has fixed this to allow other drives to be accessed -

yourusername * c:/pub;d:/somedir  xxx

I believe this is the way it was presented to work - multiple
directories could be allowed - it might also be nice to assign permissions
on each assignment also, so that different drives/directories could have
different permissions.

Anyhow the bottom line is that most implementations of JNOS code DO NOT
allow this. ONLY the NOS boot drive and the directory assigned in the
ftpusers file for the login name is permited.

This is obviously a security issue more than anything else - you wouldn't
want someone  poking around in your whole hard drive would you?

Doug

------------------------------

Date: Fri, 14 Jan 1994 22:10:41 +0200
From: Costas Krallis <[e-mail]>
Subject: TCP/IP AMPRnet publicity effort
To: [e-mail]

-----BEGIN PGP SIGNED MESSAGE-----


On Monday, January 17, 1994, there will be a lecture about
"TCP/IP Radio Data Networks" at the Technical Chamber of Greece
in Athens (The Technical Chamber is the professional body of
the greek engineers) by A.Zacharioy, SV1RD.

The lecture was prepared by A.Zacharioy SV1RD,
K.Krallis SV1XV and D.Mitrakos (U o Thessaloniki) in order
to establish the claim of the radio amateurs on the development
of this technology, starting ten years ago with the pioneer
Phil Karn KA9Q, in view of the current inrush of commercial
interests trying to exploit the technologies of the Internet.


The contents of the lecture (which can be made available to anyone
who can read greek...) include the history of data networks,
the ARRL AX.25 standard, the concept of TNC and SCC cards,
specific aspects of TCP/IP radio networks (IP over AX.25,
RSPF, ARP etc), brief description of NOS, BM, PC-Elm,
TheNet-X1j, BPQ etc and finally a description of AMPRnet,
both in Greece and worldwide.

Regards, Costas SV1XV


      +---------------------------------------------------------------+
      | Costas Krallis - SV1XV - Athens Greece (LOC: KM18UA)          |
      | Packet Radio:  [e-mail]                         |
      | Internet: [e-mail]                             |
      | S-Mail:  P.O.Box 3066, GR-10210 Athens, GREECE                |
      +---------------------------------------------------------------+

-----BEGIN PGP SIGNATURE-----
Version: 2.3a

iQBVAgUBLTb86mDaNKfCnikFAQEL9wH+PWIQMG8IVKu9dUL3w4GZAR7iCvGdz3Mc
Bi/rv+Z6KcQg3PO7Sxz5SvkM5VqnK4pNqDKsVBjKd71w3K8D/8UTqQ==
=Psjh
-----END PGP SIGNATURE-----

------------------------------

Date: Fri, 14 Jan 1994 11:11:56 -0600
From: [e-mail] (Jeffrey Austen)
Subject: TNC3?
To: [e-mail]

>Can anyone shed some light on the rumors we've heard about a TNC3?

A TNC-3 prototype is described by n7jp, n7lem and n7oo in the "Proceedings
of the 12th ARRL Digital Communications Conference," September 1993.  Some
of the features of it are:
   - two (optional) low-speed ports (300/1200 b/s and 1200 b/s)
        with built-in modems
   - two high-speed DMA ports which handle speeds "beyond" 56 kb/s
   - software based on the proposed AX.25 LAPA protocol
   - optional plug-in modems for 9.6, 19.2, 38.4, and 56 kb/s based
        on the TAPR modem design
   - CPU is an 80C188
   - capability for additional I/O cards for more ports or telemetry
The paper says that one prototype has been running since March 1993 and
a second is "undergoing evaluation."

The paper does not say anything about when, or if, it will be available as
a production unit.

Jeff, k9ja

+-+
Jeffrey Austen       |  Tennessee Technological University
[e-mail]   |  Box 5004
[phone]       |  Cookeville Tennessee 38505   U.S.A.

------------------------------

End of TCP-Group Digest V94 #11
******************************